Good afternoon, ladies and gentlemen, thank you for being here this afternoon. What I'd like to do, obviously, is to formally introduce Director Keroslowski, and then I'll read a prepared statement and then open it up for questions. Is that okay? Everyone's okay with that? We're just about right for everyone at the back of the room. Okay. Just give us a yell when you're ready. You'll have to excuse me, I'm sorry, but I've got the flu. We're good? Yeah. Okay. Good afternoon, and thank you for your attendance today. I would like to formally acknowledge Director Keroslowski from the United States Office of the National Drug Control Policy, Director Keroslowski, and I have today met with members of the Queensland Police Service Senior Executive and other invited guests to discuss the issues facing law enforcement and other government agencies around the harmful drug use and reducing the harmful effects of both illicit and illicit drugs in Queensland. For 27 years, Australia has maintained a coordinated national policy for addressing alcohol, tobacco and other drugs. This national drug strategy is a cooperative venture between Australian state and territory governments and the non-government sector. At the core of this strategy, sorry, at the core of this strategy's success is the maintenance of longstanding partnerships between health agencies and law enforcement, and both of these areas are equally responsible for overseeing the implementation of the national drug strategy through the Intergovernmental Committee on Drugs. These working partnerships between law enforcement bodies and the government agencies are the cornerstone of the Queensland Police Service's strategy in combating dangerous drugs use in this state. The current national drug strategy, 2010 to 2015, continues with a harm minimisation framework underpinned by the three pillars of demand reduction, supply reduction and harm reduction. Law enforcement agencies around Australia continue to face two main challenges at state and national levels. These are alcohol-related violence and monitoring and responding to changing patterns of use and associated harms from illegal drugs, and number two, the expanding cocaine market. Emerging psychoactive substances and pharmaceutical drug misuse are identified emerging trends under the current national drug strategy. Internationally, law enforcement is facing the challenges of new and emerging synthetic drug types along with the unconventional supply rates available to organised syndicates. The Queensland Police Service acknowledges that responding to major and organised crime, particularly in relation to drugs, is one of the most significant challenges we face. Addressing anti-social behaviour and youth violence and applying effective evidence-based drug and alcohol-related traffic, policing strategies are priorities for the Queensland Police Service under this plan. The service continues to re-evaluate our current strategies and this is why meetings like today are such an important part of ongoing responses to tackle these issues head-on. Again, thank you to Director Kerlikowski for visiting us today and thanks to the media for covering this press conference and I'm happy to take any questions as is the Director. What do you plan to do differently, Commissioner? As far as drug use and things that go, is there any radical change coming? Certainly, meetings like today give us an opportunity to, in a very, very short time, exchange ideas with national drug policy in America and I think that certainly the conversations that we had today between ourselves and a range of other government agencies with the Director and his staff have given us insights to the thinking affecting law enforcement in America. The Director has a very long history in law enforcement and I think it's interesting that he had 37 years at various levels in various police departments and he now holds this prestigious appointment within the Obama administration relating to drug policy and I think that that's a seminal point in his visit that a person from a background in law enforcement is given such a high office and a high honor. I think it's the learnings that we get from that that are most important about today's meeting. Well, it was important, I mean this is a very quick trip but one of the important parts of the trip was to make sure that we came to Brisbane and to make sure that we came to see some of the programs and projects that the Queensland police have done so in Melbourne. They had the first international conference on law enforcement and health, how to combine the law enforcement groups with public health to begin to reduce problems of drug use, violence, etc. Queensland has already been doing that. They have this rich history of cooperation that we really wanted to see. The other important part was to be able to come and learn from and listen to the people around the table to tell us about what they have done to reduce alcohol impaired driving, which is a significant problem in the United States and really more importantly for us right now what they've been doing to reduce drug driving. So, you know, this was a great opportunity for us and we wouldn't have missed it for anything and we appreciate the invitation from the commissioner and the and the department. How big a problem is methamphetamine where you come from and do you see that problem here? Well, I can tell you in the states that methamphetamine has been a significant problem. We're fortunate in in two ways. One is that we've received we've seen about a 50% reduction over the last five or six years in methamphetamine consumption in the United States and we've also seen a reduction in cocaine use in the United States during that same period. So oftentimes people say gee there's nothing you can do about these drugs people are always going to do it. When you look at those numbers it tells you that these kinds of combined works of public health and law enforcement can make a difference. It's widely circulated now that people are saying that the war on drugs has failed. What do you see we need to do differently now that hasn't been done in the last 10 to 15 years or do you agree with that? Well one we made it very clear actually and I've had the job now working for the president for three and a half years to not call it a war on drugs and to say that that really is the wrong description. The drug problem in all of our countries is incredibly complex and it's very difficult and a short-term war on drugs bumper sticker really doesn't work and I was asked well what bumper sticker are you going to use and frankly I said look I think the American public is ready to have a dialogue and a discussion around a really difficult issue and it doesn't require some some answer that doesn't work so the president's drug policy and drug strategy is a very balanced very comprehensive strategy and we're pleased to see some reductions in some of the drugs prescription drugs on the other hand and certainly marijuana use among our youth are great concern. Correct me from what wrong I think last week in last week's elections two more states voted to decriminalize marijuana use. Do you see that as being the trend moving forward towards more decriminalization and less sort of hard policing? The vote that was taken in the two states in Washington state and in Colorado is actually to legalize the recreational use of marijuana to not only that it is not a violation of law to possess marijuana that actually there would be some type of commodization of these kinds of products. Whether or not that actually occurs as we've seen with lots of other initiatives and propositions that some of our western states are able to do as it works its way either through the court process or through the legislative process we'll kind of wait and see on that. We think it's a significant mistake. President could not have been more clear opposing the legalization of drugs. The vice president's statements could not have been more clear about opposing legalization of drugs and I would think that as people actually get to see and hear and understand the science and not the slick ads that are put on to legalize drugs that they realize that you know as a way forward to keep people healthy and safe making drugs more widely and easily available is not an answer. You know that was a great myth also in the ads and it said gee if you're if you're not arresting people for small amounts of marijuana then you can really go out and solve murders. That made very little sense. Our jails aren't overflowing and they aren't stuffed with people for small amounts of drugs anywhere in the United States. That might have been true but it ended around 1995 and other crimes and other charges ended up increasing our prison population. So I don't know of any any department in the United States which is using some inordinate amount of resources to apprehend adults for small amounts of drugs. It just really isn't happening but it was a great part of the advertising campaign that was successful in those two states. Is there a bit of a problem with bikies here in the southeast? What's the states doing to sort of tackle that problem there? The problem is our low motorcycle gangs and often we found in this country a direct link between those groups and the production or the growing of illicit drugs and it is an issue here that we work very hard to to address. It's less of an issue now in the United States than it was with the different outlaw motorcycle gangs and their close involvement with with drugs. Those that that are still there and still exist are not quite to the same levels that we see either here in Australia in Canada or in Europe. But their involvement early on with methamphetamine which was an early early association of motorcycle groups but it isn't it isn't quite maybe it's because our roads are more dangerous and they're not out on our motorcycles. I don't know. Do you believe Mexican cartels are making money out of Australia? I've seen the published reports here about the cartels and the selling and I've seen the kilo price of cocaine here in Australia. It's unbelievable how high the price is. I mean one is it's very difficult of course given the continent and to actually smuggle it in so that you increase the price. What is the price comparison? What is the kilo of cocaine? I think we're at 40, 50 or 60 thousand dollars depending on purity and the time and the in the particular part of the state and I think you're well over 200 thousand dollars per kilo. Is Australia more attractive do you think? Well I think for some that can bring it in but the Mexican drug cartels have actually their influence whether it's within the United States, Europe, Africa, etc is a significant concern. President Calderon has been very courageous in taking those issues on and we've been very supportive of what he's done and actually it looks like as he leaves off us that that he's actually after after these hard hard years really begun to make some success. When you look at the reductions now this year in violence and other things taking on those transnational organized crimes groups or syndicates is important for a law enforcement throughout the world. There is some evidence of direct links with local syndicates with other South American cartels links to activities here in Queensland and elsewhere from the East and Seaboard of Australia. What advice could you share with local law enforcement on dealing with those operators? Certainly I'll defer first to the commissioner. Thank you and very obviously very interestingly we work very very closely with a range of agencies including American based agencies in terms of intelligence on drug use and drug trafficking. Certainly this is an area where we do get strong support through the Australian federal police as well so this is not just us dealing directly it is a joined up arrangement for intelligence gathering and that's the main way that the United States certainly helps Australia in trying to defeat that type of Yeah it's everybody's problem and the President Obama released the transnational organized crime strategy a little over a year ago that we were involved along with our national security staff in in putting that strategy together. You think about the global threat to the economy the engagements of all of these organized crime groups in so many crimes not just drug trafficking but extortion kidnapping etc human trafficking you know it's it's to everybody's benefit that the law enforcement cooperation the United States has with Australia and many other countries that we look at these multinational multi-discipline organized crime groups. How successful do you think asset confiscation has been in combating organized crime groups in the U.S. who have substantially made their profits through drug trafficking? There are two parts of that I think the one is that quite often we we focus on the number of arrests and the seizures of drugs and what doesn't get focused on is going after the money both in assets that they've already controlled but also in money that may be through electronic means and others and putting more time energy and focus and international cooperation in cutting off the head of the snake which is the funding is going to be really important and that's part of the President's transnational organized crime strategy is to allow the Treasury Department and to give the Treasury Department greater support for identifying assets and identifying groups organized crime groups to go after their funds. I think we should all look at how we cut off the assets. Is there one worldwide sort of Mr. Big sort of Pablo Escobar figure that you guys are looking for at the moment is there one particular or is there multiple? I think the job's open to a lot of people and it doesn't care much about country of origin or race or ethnicity but I think that as countries come together like-minded countries come together to deal with these things and then also to bring to the public's attention the fact that these groups can become not just organized crime enterprises but they can become state actors and that threat is not always as recognized in my estimation at the level that it should be. It causes significant harm and significant cost to every taxpayer and to citizens and to governments. You say state actors and that immediately brings to mind we're talking about various South American and Central American countries. Are you referring also to the U.S. then? Well I think that I'm actually referring more to some of the areas in West Africa, Guinea-Bissou in particular has been often highlighted as having all the earmarks of a narco state and yet my visits in Peru, Guatemala, Colombia, etc. I see leadership in those countries in Colombia being an example of not wanting to allow these organized groups to become entrenched but it's very difficult. I mean it takes a huge commitment of resources, it takes incredible courage and you only need to look at and as you well know I mean far better than I do the loss of the lives of journalists who have had the courage in these countries to report on cartels and organized crime. If it wasn't for them bringing it though to the attention of the public and frankly the attention of elected officials I'm not sure there would be as much courage in to take them on as has been noted. Going back to the Australian context one of the things that has been identified is an expanding cocaine market. You have had a decreasing cocaine market since I said you said what do you think are the key levers that you can pull? If I had that magic answer believe me I'd be a consultant doing something else right now but I think two things have gone on. One is I don't know anyone that doesn't consider Columbia a success. Safety, security, economy, the reduction of cocaine production from being first in the world to now number three, the increased interdiction along the east pack and the Caribbean, increased border security on our southwest border. So those are all the interdiction and the kind of the hard stuff. If you look at the soft things that I think are just equally or sometimes I'd almost say more important it's about the education and the information. You cannot go into an African American community in the United States without people telling you the dangers of crack cocaine. It is widely known and widely understood and those educational both formal and informal and grassroots educational programs about the dangers of a drug and what the cost can be in lives and the cost to young people have been equally important. So it's important that we look at reducing the demand for drugs through prevention. We interdict the drugs that are coming in and we also look at what kind of treatment programs can be available for those people that have become drug abusers and drug addicts. It's a different way selling that message to the wealthier demographic that tends to be to consume cocaine, isn't it? You know one of the things that Columbia did which was pretty interesting is that they have these beautiful prints that they have done on eight or 12 indigenous plants to the country of Columbia. Beautiful, beautiful plants none of which exist today because coca was planted in place and those plants are completely gone. And if you think about younger, wealthier, more environmentally conscious young people, you know you don't see them putting cigarettes in their mouth, you don't see you know you really see this in them. If you can explain that purchasing cocaine also leads to these kinds of devastations. It's just another different way of getting a message to a different demographic and we have to be smart about how we do our messaging but the messaging has to be fair and accurate. It can't be a scare tactic. Statistically surely this, the focus has got to go to pharmaceutical drugs now as well with the statistics coming out of the United States about how many people are dying because of pharmaceutical drugs. Do you see that same problem happening here? I do. Yeah, absolutely. I mean the misuse of pharmaceuticals, legal pharmaceuticals is a problem for us and it's one that again through education, education of doctors, pharmacists and health professionals is very, very important in trying to combat that issue. Does the pressure have to go to the pharmaceutical companies there that I don't know better control of these drugs? I think, I truly think the answer is, I mean the pharmaceuticals companies make it because of the need for these types of drugs. It is the misuse and the misdiagnosis and the misdiagnosis of the illness or it is the prescription that is inappropriately given that causes the problem and then there is the misuse of the prescription by the user at the end. Often because they are an addict and unable to control their urges and that's where the education issue is so important right across the board and that there are programs in place to deal with that. Police law enforcement, government policy can't address all of this. It's got to be personal responsibility and understanding of the implications that will have an effect overall. It's been a huge issue for us 16,000 deaths a year and due to prescription drugs and we know that about 70% of the people that begin to abuse a prescription drug get it from a family member or friend. That means it's not coming across a border. It's not being sold behind a gas station. It's coming out of a medicine cabinet. What was the one drug that really sort of... It's the opiate painkillers, the powerful opioid painkillers. I wouldn't name one in particular. There are several that come up quite often but getting people to clean out their medicine cabinets in a safe way and get rid of those expired and unneeded drugs, educating prescribers about what are the proper dosage rates and the dosage. It's a huge problem for us in the United States right now also with our active duty military and our returning veterans. So dealing with the prescription drug issue has been a focus of this administration since I took office. Is there any information you can give us comparing the level of use in Australia to the level of use in the U.S. for innocent drugs? We do have that data and based upon the survey instruments done here in Australia are a little bit different and the timeliness of those surveys about drug use are a little bit different but there are some comparisons. I'm happy to do that. We can get that to you, David. I think the key part is that sometimes people think that there's a country that is a production country and there's a country that's a transit country and there's the countries like the Americans that are big consumers of drugs and frankly those definitions are just really outdated. Every country, and I visited now 20 and three and a half years, I haven't been to a country in which there isn't a consumption problem of drugs that is causing public health and safety problems for that country regardless of the economy. Is there any one or two specific elements that you will take away from your talks with the director today that you will try or look at in terms of our drug policy here in Queensland? Certainly I think the focus on education and early intervention is critical and that's an area that I think that we can always improve in. The second one is the discussions we've had about alcohol fuel violence particularly amongst our young people and the similarities between the American culture and I think the Australian culture that use alcohol freely. Certainly there are issues there that we still I think have to work very very hard on to try and protect our youth, get them through those exuberant years without injuring themselves in a way that could be devastating to their families into the future. A classic example and we talked about this with the director is the forthcoming schoolies on the Gold Coast and the way that often parents quite well-intentioned parents and quite obviously what we would say are very protective parents suddenly turning around and buying hundreds of dollars worth of alcohol for their children to enjoy at schoolies. I mean it's a false premise and I think people need to rethink those ideas if they truly wish to make sure that their children get through schoolies unharmed and have an enjoyable time. Speaking of schoolies, are you ramping up numbers of officers this year as schoolies? Is there anything that you're going to put your own brand on as commissioning this year? No, it's our response to schoolies is a well-tried formula. It works very very well. I think we've seen what we would say are very successful in terms of mitigating the harm that is potentially there. We work very very hard. This year though we are very very concerned about the phenomenon of basically balcony surfing where the kids you know crowd out onto balconies of high rises. We don't want any tragedies and we'll be working very hard to make sure that building inspectors and certainly building managers control that particular issue on the coast. A message to parents about you know alcohol and buying alcohol for kids? A very strong message. Just don't do it. I mean the kids have the right to enjoy themselves and we all understand that and they will try alcohol. We know that but but in a reasonable amount and in a reasoned way and with the support of their their mates looking after them. I think that is that they're the critical factors and I'd encourage parents not to buy large amounts of alcohol. I think it's absolutely the wrong thing to do. There are so many other things that the young people can do to enjoy themselves on the coast during that that wonderful week which is school. We've seen this instance where students from one of the most prestigious schools in Hildes have after they've fallen and ended up at the clubhouse of an outlaw motorcycle gang. Are you concerned within some quarters of the the company that's obviously organised is the social acceptability of taking young people to a venue like that knowing full well what it is? I have no understanding of what knowledge the young people themselves had of the premises that they were going to or who organised it. I think it's very disappointing that that someone would organise such a venue for people from you know any school any high school of young people who are at that impressionable age. I don't think it was the right thing to do and I certainly think that in future people need to be more careful about the arrangements they make with perhaps third party organisers. Do you think there's a potential for it to sort of glamourise the OMCGs in a way if whatever company is that medium between the children and the venue is picking venues like that? Perhaps that was the intent of the company that did it or whoever made those arrangements but certainly I think any thinking person in the community knows there's absolutely nothing glamorous about OMCGs. The CMC's review released its report on use of tasers within the Queensland Police Service. Have you had a chance to have a look at those statistics? Only briefly I can't quote verbatim of the statistics but the report is available if you'd like specific details from it. It's basically saying that the status quo remains. There is concerns about the multiple use or multiple cycling of tasers on some people who we've had to deal with in that way. Certainly each one of those is looked at very very carefully. We have a very strong governance process as you all know over each use of tasers and we obviously check the electronic records as well to make sure that the description given by the officers or the person who's been tasered about what occurred can be backed up by that electronic record. That's a very important part of the safety net. We also do random audits of taser usage using the electronic record as well. Has there been any examples where an officer has been disciplined the taser into someone multiple times? Certainly there have been instances where officers have been given counselling and extra training because of the way that the taser has been used but we reiterate that the taser is a very very important tool in our arsenal of non-lethal force. Certainly it's a very very important tool to stop major assaults on our injuries to our officers and it's one that we're not about to renege on. Is it still the case that every officer that actually gets a taser is hit with it beforehand and how it feels like? No, they're allowed to voluntarily participate in the actual use of a taser but not all of them do and I agree that they shouldn't have to. It's certainly not something. Do you think that you know if someone's going to use a taser that they should actually experience what it feels like to know? You don't think that that would be more sort of responsible if people are aware of what it feels like? We certainly don't do it with our glocks. I don't think we do it with our tasers. Absolutely, well so is a taser. The taser's non-lethal though, isn't it? Absolutely, that's what our intent is with the taser is to stop people being using force that's unreasonable towards our officers. You don't think that every officer should experience what it feels like to be hit with a taser? Only if they voluntarily want to. Are you surprised that overall taser usage has gone up following the introduction of the taser policy? I think you've got to be careful about what type of taser use we're talking about here. Presentations are still the major use, meaning simply that the taser is withdrawn, appointed and the warning given. Many of the people that have to be addressed in this way simply comply at that point. That's the greatest use of our tasers. Rarely do we have to in real terms rarely do we have to actually use the taser but it is effective in stopping people particularly again and this is linked to the drug issue, people who are drug affected and that's born out by the CMC report again that many of those people are incapacitated in some way by or affected in some way by not just the taser but by drugs. Indigenous groups are highly represented in statistics. Is that concerning to you? Certainly the use of tasers in Indigenous particularly Indigenous interactions is of concern to me but again I say that it's used only in those circumstances where the officers have a significant fear of personal injury and unfortunately that is the case sometimes in their interactions with Indigenous Queenslanders. The tasers have cameras on? We've trialled cameras and certainly the jury's still out on that. One of the downsides of cameras on tasers is that they only are activated when the taser is drawn. Most of the issue that a taser is drawn for is not captured by the video footage or any audio. It is a real issue that the only bit that you actually see as a trait, the taser being presented towards the individual and the warnings that are given at that point in time. It is then the training for the use of our tasers is to immediately drop the taser towards the ground after it's been discharged because of a range of technical reasons. Again that means that the video is pointing to the ground. So the value, the jury is very much out on the value of the video footage from taser cams themselves. It's an effectiveness issue in relation to them. That's my understanding of the research that we've done to this point. That's a really interesting point and we invest a lot of time in training our people in communication tactics that actually try and de-escalate an issue but at a point in time if our officers are about to be attacked or basically in fear of their lives, a taser, the use of a taser is a great option for our people to have. Folks, thanks very much. I really appreciate your time today and again I'd like to just publicly thank the director and his staff for sharing this time with us. We are very, very grateful. Thank you. Thank you, Commissioner.


Felly, rwy'n fawr i'r gweithio, yw fawr yn gwneud. Ond rwy'n fawr i'r plug de-git, sy'n sylwedd y sylwedd o'r ddebyn arcafwylau'r gilrwm. Felly, mae'n gwybod i'r ddigon. Yn ei wneud i'r gweithio'r gweithio'r fawr yn gweithio'r gweithio'r gyrdd. Yn eich munud wedi'i dwyndig sy'n gweithio'r gweithio, yw yw'n golygu'r gweithio'r gweithio'r gweithio, ddweud y cwestiynau ar y ddechrau. First of all, a bit of framing. When we work on Debian, we take on a variety of different roles. The biggest difference is between when we work on as a maintainer or maintainers of our own package and when we're doing something else. And indeed everyone else who's not necessarily a Debian developer or maintainer. So I'm going to start by presenting DeGit from the point of view of everyone else. So that's NMUers, people doing sponsorship, bug squashes, downstream distros, users, teams doing cross archive work like the transitions, reproducible builds, all that kind of thing. So if you're thinking about this primarily from what you've been maintained, please be patient, I will get to you. A bit later in the talk. So the point of DeGit is that it lets everyone treat the archive as if it were a Git repository. You can DeGit clone any package in any suite. So for example, CID or experimental or Weezy, if you like, and you get a Git tree which is identical to the output of ddweud-source-x. So DeGit always works the same from the non-maintainers point of view. On any package, the operation is completely uniform. You don't need to know anything about the maintainers, version control tools, or source format preferences, or Git workflow, anything like that. Once you've cloned it, you can work on the package in Git. Just you can with any other piece of software you might have done Git clone on. So you can commit locally. You can cherry pick changes from upstream branches. You can get reset, get clean. You can get rebase-i if you have made a more complicated set of changes and you want to polish them into a nice clean patch queue. You do all the usual git-ish stuff. Stuff like log and blame is less good for reasons that I will get onto. If you have the right authority, you can also DeGit push to upload. So a ddweud can upload any package in the archive with DeGit push. The ddweud can DeGit push those packages that they've been authorized for according to the information that the archive records. We still have binary packages and we haven't quite finished with the source only uploads. So you still have to do in general a build. DeGit doesn't replace your existing build infrastructure.  But DeGit does provide some helpful wrappers for some common build runes and it's a good idea to use them because of some quirks that I will get onto later. If you don't want to or you can't upload Debian but you do want to share your work with other people, you can git push the branch that came from DeGit and that you have edited anywhere. Anywhere suitable, any git server. So you could share your branch with your sponsor who could then approve it by running git fetch to fetch your branch, reviewing your changes and then running DeGit push themselves to push your work to the archive. DeGit's branches are completely ordinary git branches can be worked with just like any normal git branch. A downstream such as a derivative or maybe a partial derivative can use DeGit themselves directly as their upstream for all of their work and then they have a completely git based setup and they can do away with source packages entirely and just have a git server. So I'm going to go and explain how this works behind the scenes now with this data flow diagram I suppose you'd call it. So it works by providing a set of git repositories in parallel to the existing Debian archive and those are on a different server which is hosted by DSA. Every DeGit push is actually two underlying operations. There's a conventional, well first operation is a git signed tag and push to the DeGit Git server and the second is a conventional package upload with a slight wrinkle. That's not shown on this slide but the DSC of an upload done with DeGit contains an extra field with the git commit hash that you pushed. So fetch and clone, DeGit fetch and DeGit clone combine information from the archive and information from the git history. If the most recent upload was done with DeGit then the dot DSC will tell DeGit what it was that was pushed and it will produce that exact git commit for you as you'll check out. If the most recent upload was not done with DeGit, DeGit imports the source package into git. That is the dot DSC it gained from the archive, imports it into git and it stitches it into the existing git history if there is one. So there is a slight issue with a rig table because if you're going to build source packages for upload you still need to get your a rig table from somewhere. So the DeGit git branches need to be treated a bit specially if you're going to do a source package based upload. If you're not doing a new upstream version then DeGit fetch will get the correct a rig table from the archive and drop it in your dot dot for you and so everything will be fine and you don't need to really worry about it. If you are doing a new upstream version then I'm kind of assuming that you will have obtained an appropriate a rig table from somewhere and if you just leave it in the conventional place DeGit will use it to build the source package. So I should mention that the only thing that updates at the moment the DeGit history on the DeGit Git server is a DeGit push. So until the packages DeGit push for the first time it doesn't exist on the DeGit Git server and even after it's being pushed to DeGit for the first time non-DeGit based uploads are not recorded in that Git server. So the history on the DeGit Git server could at the moment still be out of date and I'm hoping to improve this in the future we'll get on to my plans for the future at the end of the talk. So my view is that in general the DeGit history structure that's on the DeGit Git server should be up to the maintainer at least if they care about this. What this means for an NMU-er is that if you're doing an NMU you should produce a straight forward linear structure of commits on top of the Git commit that you got from DeGit which is what you would do with any other Git upstream. So this means not only that if the maintainer is using DeGit they can DeGit fetch your changes and then easily include them in whatever way they'd like maybe by merging them or maybe by rebasing them onto their own preferred packaging branch or whatever but it also means that if they aren't using DeGit you've at least published a history which is suitable for rebasing onto their branch or whatever else it is that they might want to do with that. Also there's another reason to do that which is that for 3.0 quill packages so if you're doing an NMU of a 3.0 quill package you should just ignore the whole quill patch system thing and not touch Debian patches at all and you shouldn't use any of the tools that maintainers are often expected to use to rebase patches about or refresh patches. You should just make your commits to the source code where you will find it in the main source of the Git repository. When you do DeGit push DeGit will examine your history it will discover that this is what you've done and it will turn your nice tidy sequence of linear Git commits into a nice tidy sequence of patches so that the non-DeGit using maintainer of your package will just see that you have done a perfectly formed NMU and will have no cause for complaining and about the only wring call is that the name of the patch of course has to be auto generated and is not necessarily the prettiest but each individual patch will have the commit message from your Git commit in it and all the right authorship information and so on. So an ordinary NMU should not normally update a patch if they are using DeGit in the quilt stack directly so you shouldn't squash your changes into one of the existing commits. This is because if you do that the maintainer may find it harder to disentangle what you've done whereas it's much easier for the maintainer if they want to squash your patch they can do that themselves very easily and they've probably got a workflow tool that will help them do that whereas disentangling it is slightly harder. Also if you attempt to do that and work in Debian patches with DeGit you're likely to get confused and generate strange broken trees that don't work properly. Another reason that you probably don't want to be working in Debian patches directly is that you will end up reading interdiffs and interdiffs are very confusing. So in summary if you're doing cross archive work or you're bug squashing or you're downstream so any workflow where you're not the maintainer you can start using DeGit right away so all people everywhere in the world have anonymous read access to the Debian archive this way and I hope it will make your life easier. Sadly unless the maintainer uses DeGit the history you see in DeGit will not be the maintainer's history. You get something that looks a bit like this there's a synthetic commit generated by DeGit which is an archive import. The reason for this is that maintainer's git branches often indeed sometimes even usually differ from the source package in the archive. If you have if you DeGit cloner package and the package as comes from the archive has an ex VCS git header nominating some git repository that the maintainer prefers to use DeGit will set up a remote for you so you can fetch the maintainer's history and use it if you think that's going to be informative. So in that sense you can use DeGit the same you know you can use DeGit to do the same task as dev checkout but in general the ex VCS git tree is not necessarily usable by somebody who doesn't know what the maintainer does with it. So DeGit doesn't use the branch found in ex VCS git as a basis for anything. So difficulties that arise with ex VCS git that you often find is there are repositories out there where the ex VCS git header names a repository that contains only a Debian directory and no upstream source code at all or it might be a 3.0 quilt tree where there's a Debian patches directory and a pile of patches in a quilt stack but those patches haven't been actually applied to the source code in the tree. So git build package for example likes to work with those and the tag and sweet naming conventions can also vary. So while the maintainer's history is useful in the technology so you can have a look at it for git blame and git log it's not in the general case suitable for the use of DeGit unless the maintainer is using DeGit and therefore DeGit can't really rely on it and doesn't use it. Another problem with ex VCS git is that of course the maintainer's git server could be anywhere so it might be down or it might no longer even exist or it might have been compromised. So that's why if the maintainer didn't push with DeGit DeGit has to synthesize git history and the synthesized git history has this very basic structure. So that gets me on to the second part of the talk which is DeGit for maintainers. So for these reasons downstream git users would like you as a maintainer to use DeGit push to do your uploads. They'll then be able to see and directly work with your own history and they'll get that much richer history. And from a more general point of view the point of using a DVCS like git is to publish your work and the existing ways of publishing git histories for Debian packages aren't uniformly usable for users. The ex VCS git system gives you some git branch but the user can't rely on being able to use it directly they'll have to understand if you are a user who's working with lots of different packages you'll have to understand every maintainers special snowflake workflow and there are people who have done that and have internalized all that knowledge but I don't think that's for everybody. So what DeGit does from the maintainers point of view is it provides a way for you to publish a history which users can immediately rely on corresponding exactly to the archive and therefore the users of DeGit history can rely on using that history that you have published without needing to know anything about your workflow. But there's another selfish reason why you would want to upload a DeGit. If you use DeGit you'll be able to directly merge NMUs branches that you see and maybe pull request emails other kinds of similar contributions because in this case the DeGit using contributor will have based their work on your history. So their push will be fast forward of your last push. If you didn't use DeGit then they will be working on this stub history like you see on the left here and they'll make commits based on that stub history. So you can still DeGit fetch that work if you're not using DeGit to do the push but you're at the very least going to have to rebase NMU's work onto your own branch or maybe you'll have to use a non-Git based method of importing an NMU like a Git import DSC. So another advantage for using DeGit push is that it will put your actual history on browse.deagit.debion.org which is the Seagit view of the DeGit Git server rather than advertising DeGit's stub history which also might be out of date as I've discussed. And if you use DeGit push you get an extra check that the source package you're uploading is exactly the same as your Git head and that can save you some checks based on your DSC. It makes it for example more practical to do your upload tests in a Git-ish way and not have to run tests on the DSC. And of course as I say doing your uploads of DeGit will improve your users and downstream's lives. So back to this sort of data flow slide DeGit is not a replacement for any of the existing Git packaging tools it's intended to complement them so unlike Git DPM DeGit does not define a Git history structure the history structure can be anything. It doesn't define or suggest naming structures for upstream or downstream branches, pristine tar branches, whatever and it doesn't require a particular source package format it couldn't since it needs to work with any package in the archive. DeGit rather imposes only two requirements on your Git trees and these requirements stem directly from DeGit's objectives. The most important requirement is that your Git tree is identical to the unpacked source package. This is the whole point of DeGit because it enables DeGit to always present to the user a working tree which is the same as they would get from app get source. So considering that requirement for all native and source format 1.0 packages which includes anybody using raw Git to manage their delta from upstream a Git tree identical to the source package is already the interchange Git branch format. So if you're using format 1.0 you can start using DeGit right away for all maintainer uploads. So that includes all native packages and anything that's using any maintainer who's using 1.0.diff. For 3.0 quilt packages things are a bit more complicated. So the purpose of DeGit is to provide a Git view that's identical to the source package and can be worked on without knowledge of the maintainer's source format. This means that the DeGit Git tree for a 3.0 quilt package is what I think Raphael has called a patches applied packaging branch without .pc directory. What that means is that all of the changes made in Debian are represented both in the main source tree and in Debian patches. So for example if you add a new command line option to the program in a Debian patch there will be a Debian patch file in Debian patches whatever adding that command line option but that command line options that patch will be applied and the command line option will be present in the main source tree. This is obviously necessary so that somebody who doesn't know anything about Debian patches when they get the Git tree they're able to grab the source code and look at the main.c and see what the command line options are and not miss that this option would be there in the Debian package. So the most popular tool for working with 3.0 quilt I think probably I don't know if there's been a survey of this but it's probably Git build package and Git build package likes to work with patches unapplied trees. I'm sure about this the Git build package maintainer and we've had a couple of really good conversations we do have a plan for interoperating which involves DeGit synthesizing an additional commit or commits to apply the patches and pushing that synthesizing that is privately not applying that to the maintainers branch but that's what gets pushed to the DeGit Git server and I think it would be possible to integrate things this way I've done a bit of experimentation and that seems like it's going in the right direction So this patches applied versus unapplied problem doesn't apply to Git DPM which is I think probably the other most popular tool that people are using to manage 3.0 quilt packages but there's another problem which affects both Git build package and Git DPM Neither of these put the .gitignore or changes to the .gitignore in the source package that is you end up with a if for example the Debian maintainer adds a .gitignore the .gitignore occurs in the Git tree but does not occur in the source package and this is because they tell Debian source to ignore it when building the source package so this obviously is a problem and the reason that they do this is because they don't want to generate a patch in Debian patches that corresponds to the additional change to the .gitignore the 3.0 quilt source format can't represent the .gitignore any other way so that would be necessary I've spoken to Bernard Link about this he wasn't very keen on having Git DPM treat.gitignore normally and record.gitignore in a patch in the Git DPM branch so I mean I'm still talking to Bernard about this but if we can't think of a better solution then in much the same way as I'm proposing for Git build package DeGit will have to synthesize this .gitignore patch and effectively commit it privately on to the DeGit Git branch at the point of push so as to convert your Git branch into one that's both directly editable and equivalent to the source package right so there's a few other things I ought to cover since they often come up this sort of set of leftovers essentially is relevant to both maintainers and non-mainteners there are so firstly there's a few wrinkles I need to cover the first wrinkle is that DMs that's Debian maintainers who authorize to upload to only parts of the archive those people currently need to email me a signed copy of their SSH key before they can push this is because the DeGit repo server uses SSH as the transport and the Debian project does not right now have a systematic record of all DMs SSH keys we do have that record for DDs but not for DMs so there's some kind of ad hoc mechanism where I add the key the second thing that's less than ideal is that the DeGit Git history doesn't generally include the package upload history so you'll have seen on my slide here you get just this little stub Git import DSEs this can produce a Git branch more or less representing upload history but DeGit doesn't run that itself it would be difficult for DeGit to do that because it would have to decide which set of packages did it want to run that on and it would be a great deal of download and computation to run on the possibly the NMU as system now there's nothing saying that one couldn't push such a branch to the archive with DeGit push or indeed that there could be some kind of server side process that would generate such history and store it in the DeGit Git servers Git branches but so as I said earlier it seems to me that the Git history structure ought to be up to the maintainer and if the maintainer chooses to use DeGit then the maintainer's Git history is obviously much better than the import DSE snapshot based history so I think the real way to improve this situation is to persuade more maintainers to use DeGit if we discover that a lot of maintainers don't want to use DeGit you know at some point we will consider centrally maintaining a snapshot based history at the DeGit Git server but the most obvious challenge is DeGit's insistence that the source package and the Git tree are the same so sadly quite a few source packages contain files that aren't in the maintainer's Git branches but which are needed to build so there's not just .gitignore which isn't really needed to build but the most common example would be auto tools output so there are a lot of workflows that seem to involve having a source package that contains the auto tools output but a Git branch that doesn't such a Git branch is not usable with DeGit because the point of DeGit is that the user gets the same thing as the source package I don't think this is a terrible problem because nowadays the recommendation mostly seems to be that the package build should always rerun auto tools and if you do that then neither your Git tree nor your source package contain the auto tools output and everything is fine if that's not the workflow you want and there's some reason you don't want to do that then you can commit the auto tools output to Git this sometimes gets you merge conflicts you can resolve those easily just by rerunning auto tools and the second way that DeGit's rule seems mostly to byte is .gitignore and we've discussed that in the context of 3.0 Quilt most existing build tools remove .gitignore from the package build so even if you're using 1.0 source format your source packages don't include your .gitignore even though your Git tree did and this is why DeGit provides these wrappers you'll see there in the third synopsis line for the build operations if you use those tools to build for upload DeGit will pass some appropriate .i options to deep source to exclude exactly and only the .git directory and with source format 1.0 this is sufficient there's a compelling advantage of DeGit's Git based approach which you'll probably notice if you do cross archive work many packages have very strangely behaved buggy clean targets because DeGit knows that your Git tree is canonical it can help you work around this problem so you can just tell DeGit to use Git clean instead and never run the packages clean target if you're not in the habit of forgetting to say Git add then you can set a configuration option to have DeGit always use Git clean and then you'll never have to fight a buggy clean target again so I've got a few plans for the future which some of these I may even get around to I need to implement this automatic adjustment that I discussed earlier for Git build package and Git DPMs Git trees so that users of those tools can do DeGit push with 3.0 quilt and it's possible that they will have to be or that they're all to be some additional tooling to help those users deal with NMUs in a sensible way DeGit can't currently upload to delayed queues which makes it a bit awkward for a kind of fire and forget NMU so I've thought about how to implement this the obvious implementation is just to divert the .dsc the changes file to the delayed queue and immediately push but have DeGit still immediately push the upload to the DeGit Git branch but if the maintainer deleted that upload from the queue with de-cut the changes would still be present in the DeGit Git branch and so a future DeGit user would see that upload would look just like an upload that was stuck in a queue somewhere and if they then upload based on the DeGit branch the changes that were de-cut by the maintainer would be resurrected and I think that would be unpopular so at the very least there needs to be some way for a maintainer to revert a push which was accompanied by a delayed upload but I'm not convinced that maintainers are going to be happy having to do some special thing to undo some oh this DeGit weird tool did some strange thing and now I have to fight it so a better implementation would be to have the push DeGit branch stashed away in some corner somewhere just like the just like the source upload is and then at the appropriate point it would be revealed when it was ready if it was still a fast forward that makes it trickier for somebody else to find it if they want to work on top of it there might have to be some special option to fetch to say oh I actually want this delayed NNU because I need to update it and it's more work to implement but I think it will probably reduce the possibility for other maintainers becoming upset it will be very easy for DeGit when it is doing an NNU to construct the NNU diff that you're at the moment required to email to the BTS of course the maintainer can fetch your NNU as a Git commit easily with DeGit fetch but if the maintainer probably doesn't want to do that or maybe isn't using Git at all and you're supposed to comply with the existing policy so you have to send this email so I think DeGit should probably just construct that email itself and that has a few advantages because for example the DeGit generated email could specify the exact Git commit range that was pushed in a URL to fetch it from which the maintainer might find helpful along with the conventional debdiff when you're doing a source only upload you have to do slightly more work then you really should have to because there's no real need in that case for a separate build source package step so I think there should be easy way to have DeGit push generate the source package at the same time as DeGit push would generate the source package rather than you having to do it in advance since it can easily do so where are we right so the DeGit Git server has now a lot of access control machinery it knows who's a DD who's a DM it can receive signed updates to Git repositories so it's got most of the moving parts to become a fairly general purpose Git server with access control equivalent to the Debian archive so in this role it could replace some uses of Alioth which I think would be useful because Alioth is doing too many other things and isn't quite the right shape and Alioth is also I'm sure the Alioth people would not mind me saying this but Alioth is in need of help with its administration and care and feeding so taking that load off Alioth and using something also with better security properties would be an improvement so in particular I'm thinking of arranging that you can do signed pushes if you have signed pushes then a fully git-ish packaging workflow where you just pull the branch from the Git server and you can know that that branch was pushed already by somebody who was authorised at the time and there's some traceability of where that came from at the moment with Alioth or indeed any other Git server that's not really true I suspect many maintainers probably don't check what they find in their Alioth VCS Git master branch anyway and they probably often just push it knowing that it's the thing that they pushed themselves yesterday but in principle that's not good Digit requires the sweet branches to be fast forwarding if you have a workflow involving Git rebase you need to make a fake merge so one made with git merge-s hours at the tip of your own branch to make it be a fast forward to the previous state of the Digit sweet branch and when you want to work on the package again with Git rebase you'll need to strip that fake merge because Git rebase will choke on it you can do this you can do all of this with raw Git operations if you're a Git expert, Git merge and Git reset have all the relevant functionality but it's quite ugly and doing it by hand lacks some important safety catches so I'm intending to provide some tooling that will make this easier and make a fully Git rebase kind of workflow easier and the final thing I can do myself is arrange for non-Digit uploads to be automatically converted to history in the Digit Git server which would make the Digit Git service history at least not be up not up to date there are also some things I need help with so the documentation for how Digit works together with existing Git management tools is a bit out of date so ideally I think each Git management tool Git workflow tool would explain how or whether it works with Digit and it should explain for example what additional requirements there are that you have to sort out if you want to Digit push and how to incorporate changes made in an NMU into the tool's own favourite workflow and history format how to update a package to a new upstream version some of the maintainer tools don't cover that I'm spoken to the Git build package and Git DPM maintainers and I'm optimistic about that this is going to come particularly about Git build package finally there's a not finally, nearly finally there's a difficulty with empty directories in source packages Git refuses to handle or track empty directories I won't go into that in too much detail since I'm running a bit short of time there's a few exciting finally possibilities for new uses of Digit it would be very nice to have a way for a sponsor to provide a Digit-ish Git branch which the sponsor could work with directly and ultimately Digit push when it was ready I want to talk to people familiar with the sponsorship infrastructure about this when I had a look earlier about this a week or two ago sponsors Debian that seem to be down I don't know maybe there's some help needed there and secondly Digit is not just for Debian other distros currently using source package based workflow can use it too so we've read only support even any specific support at the distro end so you can Digit fetch from Ubuntu right now patches for read only support for Mint should be quite easy to or any other derivative should be quite easy to to provide Digit push support for a particular distro requires infrastructure support it needs a new Git server that ought to be under that project's control and it might need some thought so I hear rumours that Ubuntu might grow a Digit Git server and support Digit push and I just wanted to say that patches in that direction are also very welcome and finally there are some people I need to thank at least half of the design of Digit is Joey Hesse's at the now famous cardboard diagram session at Vilmarcu where we sketched it out on an old cardboard box DSA and particularly Peter Pylfrada have been absolutely brilliant and level of service and competence has been really outstanding every time I thought of some aspect of the setup I've forgotten and made some blaver as an ill thought out request a DSA would propose a much better alternative and implement it their end of it almost immediately I also like to thank the FTP Masters data service which has enabled me to extend Digit's usability to non-DDs and non-DMs so that's what I've preferred and there's a lot more detailed information in the man pages but I think we still hopefully have some time for questions are we going to do this with a roving mic? if you want to ask questions please go to the microphone you've sat in the wrong spot Manoj sorry use the roving one okay that seems to be on okay so you started introduction by saying that Digit's task is to represent the archive as I get remote and you're going through great length to make sure that individual commits that are there correspond to the content of our source file but it seems that you're mostly unless in the things to do list ignoring the fact that the Git repository is mostly about the history so I would have expected the first thing that you do is to have the complete history of the archive as a Git branch and then think about how you can maybe have each of these commits representing actual uploads have a secondary or tenary or whatever parent into the that's the actual Git history of the maintainer at least that seems something that I would prefer to see from Digit that there's a clear branch that I can look at and it's just commits representing uploads and then the maintainer Git history gets merged into that as a parent is there a reason why you didn't attack it from that angle yes because that's harder and less immediately useful so if you think that's important and you would like to arrange for the Digit Git server to have that Git history for all packages that have been uploaded to the Digit or all packages at all then I'm you know I'm happy to have help and there'll be obviously some server side work to be done there but yeah help very welcome is there any requirements on the local build infrastructure to using Digit do I have to use sbuild no you can use whatever you use to build packages right now obviously you should be using sbuild or maybe pbuilder but if you're not there's nothing stopping using digit and all it needs then is a .dev file in some well known location so when you say digit push it will expect to find in the parent changes that your build produced and it will so all the signing is done at the time of digit push because that's the atomic that's like the commit operation so at that point it will take your changes file and it will write the commit hash into the dsc re-edit the changes file sign all of the things and upload the result and your changes file presumably will include whatever binaries are required just sounds really useful I'm definitely going to use this but first of all thanks a lot for their works I'm sure that will help for a lot of NMUs and small packages which don't really warrant their own fancy history and I've got one question about NMUs, would it be possible to represent the stuff that is in delay queue as branches other than master in Digit so that you can access them if you want but they don't necessarily look like they would already be in the archive yes I think that would be the sensible way to go about that problem there's some there's going to be some slight wrinkles there because the way that the delayed queue works and the way that a second branch that you'd have to have maybe branches named after the date at which they would be uploaded or something I figure you would have to change like a branch delay2 delay3 delay4 and then update them every day or maybe there'd have to be some cron job that would on the server and you would see when the thing appear to the archive and go oh I'm supposed to shuffle this commit across now or maybe you can even get a notification from the delayed queue that said please update your branches now I just moved everything across from the delay3 so actually if it were in a second branch and then you did digit fetch because the .dsc would have once it's been accepted into the archive the .dsc would have a commit hash in it it would automatically use that commit on what it found on the git server so the suite branch is mostly it's there to record uploads that haven't made it into the archive yet but for uploads that are in the archive it's just really it's just there because git needs a ref to cause the objects to appear and it's the .dsc that really tells you what the value of the suite in the archive is so you just said that if you do digit push it it goes looking for a changes file and put a letter bit and then upload it is there any checks in place if you accidentally made a change after you last built and forgot about it then digit push that then it's no longer in sync yeah and digit will detect that and it will complain which which suites are supported I guess all suites are supported also proposed updates and other stuff any suite that is in the ftp master data service API is supported it is possible that there are suites that have strange properties that I don't know about where if you do digit clone squeeze wheezy proposed wombat needles that somehow exists in the ftp master data service API and I don't know about and if you run that maybe there's some strange bug that occurs but in principle every suite is supported that is on in the archive at all how are those merged for example if there is some NMU into experimental and an MNU based on that in unstable what would the history would the history be merged so if no the digit doesn't merge history from different branches if you do digit push then the history is just what you push so if you do digit fetch from experimental and then push to unstable the thing that you push to unstable will be a fast forward from experimental but you'll have to merge it because it will have to be a fast forward from unstable as well if you if you don't do a digit based for non-digit based upload the synthetic histories on the different suites are just constructed ad hoc and they constructed client side not server side hi to two small questions the first one you mentioned that you generate debent pages automatically somehow is it a git format page or is it something different I think it's duplicate source-commit ok the reason I'm asking is if it would be git format page upstream could just git AM the page directly from Debian which I as an upstream would find totally awesome are patches generated by deboost-commit usable for git AM great no no that was a question are they oh I don't know far that is a bug against duplicate source true and then so the reason I do it like that is because the quilt 3.0 thing is quite complicated enough already without digit kind of opening up the cover and starting to mess around with the insides as well so deep good source tries to pretend to deep good source that it is just a very sophisticated maintainer who knows exactly what to do and therefore and that's why for example I generate patches of the deep resource commit and arranges for a digit itself to be re-invoked as the editor so that it can supply the right commit message ok, thank you and the second question is did you ever encounter an oryctable that contains .git attributes or git modules I have a bug open about .git modules and the answer is .git modules doesn't actually cause any trouble git attribute will git attributes might if you have example packages of like weird pathologies in them nothing in the archive because that's what pretty much non free but I do have an upstream which generates such a top well if you have a thing that looks a bit like a source package that you think it won't work with send me the bit somehow because these wrinkles ought to be sorted out if at all possible thanks sorry for the remaining question if you could ask after the talk outside to let some time to the others to prepare for the next one and thanks for the presentation ok, thank you


مقدس I begin the name of Allah the most beneficent, the most merciful praise be to him the creator and the sustainer I begin his name Allah سبحانه وتعالى and I send my peace and my blessings upon Mohamad and his holy progeny and I send my condolences to the Imam of my time صاحب العسري والزمان من الله حيست in his reappearance on the marcherdom on the tragic event of the attack and the killing of Fatima al-Zahra'a peace be upon her on the marcherdom of Fatima al-Zahra'a peace be upon her we continue where we left off in our previous episode we spoke of the interaction between Rasoolallah peace be upon him and his holy family and Amir al-Mu'mineen as they were walking through the gardens with his companions and he told them as he began to cry as his tears began to flow my prophet peace be upon him he told Ali ibn Abi Talib there is hatred and malice in the hearts of some in my ummah they will not unveil these feelings until after i pass away we will continue discussing the prophecies of Rasoolallah peace be upon him and his holy family concerning the malice concerning the hatred that Quraysh had placed forth on his holy household the following hadith can be found in Al-Manaqib of Al-Khawarizmi page 62 in Al-Alam Al-Majdisi recorded in his bihar volume 27 page 45 listen to the words it might be similar to the previous hadith but it is good that we repeat and there is a different context through this hadith oh Ali the enmity and malice in their hearts towards you will be unveiled after my death those are the ones whom Allah curses and the people curse them too ويلعنهم الله ويلعنهم العنون صورة البقرة verse 159 those the ones that have hatred towards you عليبنا بطالب and enmity towards you those hypocrites from my umma are the ones whom Allah has cursed and the ones that the people curse curse in the meaning that may Allah remove his mercy from them then he says after he begins to cry my prophet peace be upon him and his holy family begins to cry and speak to عليبنا بطالب علي علي تلز رسول الله يتلزم يا رسول الله why is it that you cry seeing the message of Allah peace be upon him and his family crying breaks the heart of عليبنا بطالب عليبنا بطالب tells him the archangel جبرايل has informed me that they will oppress him oppress عليبنا بطالب deny him his rights fight him they will kill him and after his passing oppress his children and kill them too يا أموة محمد oh nation of Muhammad what have you done to the household of the prophet like we said before you listened and you enacted the commands and the instructions of the prophet with the christians and the jews and you killed the closest family of Muhammad you murdered the lady in which Muhammad peace be upon him used to come to her house and ask permission to enter he would stand in the door and say may Allah purify you oh people of the household through purification you murdered the lady of light in which the final messenger of Allah peace be upon him and his holy family would ask permission from peace be upon her to enter the house you murdered this lady did you ask for her permission when you forced the door on her and kicked her stomach and took the metal end of the sword and slashed her and slapped her on the face and left a wound on her body did you take care of the family of Muhammad the next hadith here the next hadith will show you the hypocrisy of Quraish the hadith is found in تخريب المعرف of the sheikh Abu Salah Al-Halabi رضوان الله تعالى عليه by Al-Qasim ibn Jundab he said from Anas ibn Malik from Anas Anas says عليه عليه السلام got very sick and became weak the prophet had entered upon عليه ibn Abi Talib and i was sitting by the head of Ali ibn Abi Talib i moved and he sat by the head of Ali ibn Abi Talib and he began to greet him and condol him Abu Bakr and Omar were sitting in the majlis Abu Bakr and Omar were sitting in the majlis Abu Bakr winked at with his eyes he looked towards Omar saying talk to رسول الله speak to رسول الله peace be upon him Omar got up and listened to these disgusting words no respect to رسول الله no respect to أمير المؤمنين this is a fact this is a fact this is the character of Omar ibn Al-Khattab he knew that we are narrating to you read his biography read his biography and you will see you will see his character he said oh messenger of Allah you have entrusted promised us that this man will have authority yet i do not see this happening anytime soon if he passes away whom or who will take his place who will take his place the messenger of Allah صلى الله عليه وسلم did not respond to Omar ibn Al-Khattab Omar and Abu Bakr repeated their actions three times and to رسول الله peace be upon him and his holy family responded he said this man will not die from this sickness he will not die until you fill him with anger, betrayal and oppression but by Allah you will see Ali ibn Abi Talib patient he said you too he will not die because of this sickness he will die because you you too will instill him with betrayal and oppression and anger this report is found in الخصائص of a Siyuti volume 2 page 124 المستدرك volume 3 page 139 and as i said in تخريب المعارف as well it can be found in تاريخ دمشق volume 18 page 33 in كتاب سولي مبنو خيس الهلالي this is a reliable book that we have this historical book that we have this historical book that we have there is an addition the addition is the following after رسول الله got up he said the same words then he said you will see him patient and obedient to Allah سبحانه وتعالى he will not die until he faces corruption and evil from you too from you he will be killed and he will die as a martyr this is the word of رسول الله to these two disrespectful people you see the way they spoke to رسول الله and how is amir al mu'minin going to die a martyr a patient one too قريش has a problem with بنو هاشم from a while back قريش has a problem with the message of Islam رسول الله took them from darkness into light he took them from the time of جاهلية to the time of enlightenment he gave rights to women Islam brought forth equality Islam brought forth laws that قريش disgusted and did not like of course قريش how else are they going to destroy Islam they use the excuse of the testimony of Islam they did the shahada they wore the attire of Islam they said to the people we are Muslims and you see after the march of رسول الله they left the body of رسول الله they did not do the the funeral processions of the body of رسول الله and they went and they appointed themselves a leader as they say through democratic votes tell me a moral rational man does he accept that الله سبحانه وتعالى leaves the ummah with no leader and no divine successful leader and lets them vote democratically for a human lets them vote democratically to appoint a Khalifa the rational the human being does not accept this of course this is another discussion we will continue looking at the siyaq of this hadith so insha'Allah we will complete the hadith this section here will be the khitam of this hadith God willing insha'Allah in the reports in the book of Suleim I will read to you the Nass of رسول الله من these words حتى you know how much oppression أهل البيت faced from qurash and how patient amir al mu'minin was the greatest characteristic of amir al mu'minin is not his courage but it is his patience Oh Ali after me you will see intense betrayal and oppression from qurash if you find people to age you then fight them if you do not put down your weapon and do not spill blood and do not lead yourself towards destruction you are to me as haroon is to moussa follow haroon's footsteps and remember when his community thought he was weak and wanted to kill him hence be patient over this oppression you are to face from qurash for you are like me like haroon was to moussa like haroon was to moussa and they are like the ones who follow the samurai now a point might be asked here is amir al mu'minin weak can he not face them alone this is because of Allah's divine wisdom first secondly there is a hadith by رسول الله which states that the example of Ali ibn Abi Talib the example of Ali ibn Abi Talib is like the ka'bah we go to the ka'bah the ka'bah does not come to us الله سبحانه وتعالى wants to test the ummah he wants to see will they come to Ali ibn Abi Talib only when they come to Ali ibn Abi Talib when they want to aid Ali ibn Abi Talib when they want to have a divine recipient of Allah سبحانه وتعالى when they come to Ali ibn Abi Talib when they want to aid Ali ibn Abi Talib when they want to have a divine recipient of Allah سبحانه وتعالى سبحانه وتعالى على this earth that is when علي كن fight them if not علي sit down put down your weapon and do not let this ummah go into this unity because if anything happens right now it will affect my Shi'a after now listen listen to this point right here he says Oh Ali Allah has decreed to place this unity and opposition in this ummah in this nation if Allah wanted he would unite them all on guidance until even two people from his creation would not quarrel in any of his matters if Allah wanted he would send his punishment sooner and withdraw his bounties until his oppressors would be proven at fault and the truth would be known with whom it is but he has made this he has made this world a place for trials and tests and makes the hereafter a never ending abode he may recompense those who do evil with the penalty of what they have done and recompense those who do good with the best reward Surat An-Naj verse 13 رسول الله صلى الله عليه وسلم told Ali ibn Abi Talib if ya Ali if Allah wanted he could have easily united the ummah that there would not be Khilaf between two and he caused this unity and oppression in this ummah he caused this unity sorry and confusion so that he may test the ibad if Allah does not test us then what is the point of being here this would be against the hikmah of Allah سبحانه وتعالى the justice of Allah سبحانه وتعالى where would morality go where were ethics go hence it is divine test for the ummah the example of Ali is like the Ka'bah we want people to come to Ali ibn Abi Talib the Ka'bah does not go to the people Ali tries yet the ummah does not want Ali ibn Abi Talib do you now see the oppression that Ali ibn Abi Talib peace be upon him faced from this ummah did you not see the oppression that Fatima Tezzahrae peace be upon her faced from this ummah this is the Ahdal Bayt peace be upon them oppressed since the march with them of Muhammad everybody turned back on their heels they rejected the appointed leader of Allah and they chose themselves a new leader ان شاء الله in our next episode we will begin to tell you the prophecies that Rasool Allah for told us Ahdal Bayt concerning the affliction that they will face from this ummah peace be upon you my lady Fatima and may Allah hasten the reappearance of my master امام المهدي والمنتظر عجل الله تعالى فرجه الشريف والسلام عليكم ورحمة الله وبركاته


Energy sectors are the core determinant of inclusive economic growth. Traditional energy resources, coal-oriented, have a higher negative impact on nature and people's well-being than on economic and social benefits. Digitalization of government could be a core instrument for handling the above-mentioned issues. This article was authored by Alexei Kulinsky, Alexei Liliov, and Tatiana Pimenenko.


Oh Jesus, we come to You Oh, we lift our words of ever-gain I give it for there's nothing in this world